It will be in the next release in approximately two weeks time

This has just been released to maven in 0.31.1-alpha

Is it somehow possible to hoist the webViewState and the navigator above the NavHost? So for example in the WebViewSaveStateSample.kt to call the rememberSaveableWebViewState() and the rememberWebViewNavigator() just right after the rememberNavController() call and then pass down the webViewState and the navigator to the Home composable via arguments?

So something like:

val navController = rememberNavController()
val webViewState = rememberSaveableWebViewState()
val navigator = rememberWebViewNavigator()

LaunchedEffect(navigator) {
   val bundle = webViewState.viewState
   if (bundle == null) {
      // This is the first time load, so load the home page.
      navigator.loadUrl("https://bbc.com")
   }
}


NavHost(navController = navController, startDestination = "home") {
   composable("home") {
      Home(webViewState, navigator)
    }
   composable("detail") {
       Detail()
    }
}                   

Because for me this doesn't work. With this approach the webview is not keeping the state after navigating. Any idea how to make this work?

Is there a way to remember WebView state which is in a LazyColumn item? I'm testing the rememberSaveableWebViewState but when I scroll away from that item and go back to it - WebView refreshes the page.

I put a webview into a ScrollableControlView, Then I click one button, and the page navigates to annother page. Then, I back to the webview page, the webview refreshes the page. It loss its scroll position.

Box(Modifier.fillMaxSize().verticalScroll(rememberScrollState())){
Button(Modifier.click(gotoAnnotherPage)){ Text('NEXT PAGE') }
WebView(Modifier.fillMaxWidth().wrapContentHeight())
Text('Hello , this is a test!')
}

Is there any way to remember the scroll position? Thank you!

Thank you @bentrengrove for adding this functionality, I think it's a great step in making webviews easier to manage with compose. I wanted to second the use case that @rafakob mentioned above. I have a small webview element being displayed in a lazy column that I can't revert to a non-recycling column due to performance concerns, and the reloads are quite jarring from a UX perspective. Will be following this thread to see if there are any updates/plans to help support this use case in the future.